don't miss to do a npm I at root of the repo to sync the lock file 😁
Also you can use multiple step codemod to separate job if needed like for https://github.com/nodejs/userland-migrations/tree/main/recipes/node-url-to-whatwg-url

For dependency removal I'm asking the Codemod team. because on V0 when the tools was JS only and there was a simple thing to manage dep

@AugustinMauroy the PR is still a draft, no need to nitpick yet

@AugustinMauroy the PR is still a draft, no need to nitpick yet

😅 oops I'm flash macqueen. Nop kidding just inattentive

@AugustinMauroy I've pushed a few commits which I believe address some of the earlier comments. From the original Github issue, 7/8 test cases are passing. The one test case remaining is the complex chaining example.

const styles = level === "error" ? chalk.red.bold : chalk.yellow;

const styles =
	level === "error"
		? (text) => styleText(["red", "bold"], text)
		: (text) => styleText("yellow", text);

I have a rough idea/implementation locally for this, but it's a bit nasty and I'm not sure I like it.

But I'm keen to get feedback on this initial approach and understand if there are possibly better ways of implementing.

I'm going to review your current code.

LGTM for now the warning si good. Missing some piece that already in the todo.
If you doesn't want to do the dependency part I can do it in follow up pr.

LGTM for now the warning si good. Missing some piece that already in the todo. If you doesn't want to do the dependency part I can do it in follow up pr.

Here's my plan for the remaining work:

• continue working my way through the remaining TODO's unless I run into any blockers.
• pull down some open source projects that use chalk and run the codemod to iron out any unforeseen issues
• take a look at the removal of the dependency

Okay nice !

the complex chaining handling is clever 👌🏻

@AugustinMauroy I've pushed some commits that close off the remaining TODO's that were left from last week. I've also made an attempt at the dependency removal process that you mentioned above.

I've also done a bit of testing with this implementation across some open source projects that use chalk. It is largely working as expected, although I found some interesting use-cases which are not currently handled in this PR:

• Complex template literals

console.log(`You can now view ${chalk.bold(appName)} in the browser.`);
console.log(`Server running on ${chalk.cyan(`http://localhost:${port}`)}`);
console.log(`To build, run ${chalk.cyan(`${useYarn ? 'yarn' : 'npm run'} build`)}`);

• Nested chalk calls

console.log(chalk.underline(chalk.red("error")));
console.log(chalk.bold(chalk.yellow("warning")));
console.log(`Search for ${chalk.underline(chalk.red("keywords"))} to learn more`);

I'm happy to take a stab at those in this PR, although the amount of files now is starting to grow. It may make sense to do in a follow up. WDYT?